Life cycle management of user-selected applications on wireless communications devices

ABSTRACT

Tools and techniques for performing life cycle management of user-selected applications on wireless communications devices are described herein. In part, the tools provide machine-readable media for presenting to the subscriber a list of available applications for installation on the device, and for receiving selections from the subscriber of one or more of the applications. Additionally, the tools provide methods for selling advertising space on the devices.

BACKGROUND

As wireless communications devices become more powerful andsophisticated, an increasing number of applications are becomingavailable for these devices. Additionally, different makes and models ofsuch devices continue to proliferate. As the market for such devicesexpands, different types of customers may consider purchasing and usingthese devices, and installing different applications on those devices.

Typically, the customers manually install the applications onto thedevices, and thereafter maintain the applications manually, includingun-installing applications. In some cases, installing and managing theseapplications may be a challenge, particularly for inexperienced orcasual customers. For example, it may be difficult for a customer todetermine whether his or her device meets the minimum configurationspecified for a given application of interest. Once the application isinstalled, customers may not be aware of subsequent updates, bug fixes,or upgrades available for the application, unless the customersproactively search for these items.

SUMMARY

Tools and techniques for performing life cycle management ofuser-selected applications on wireless communications devices aredescribed herein. In part, the tools provide machine-readable media forpresenting to the subscriber a list of available applications forinstallation on the device, and for receiving selections from thesubscriber of one or more of the applications. The tools provide amechanism for removing applications from the device. Additionally, thetools provide methods for selling advertising space on the devices.

BRIEF DESCRIPTIONS OF THE DRAWINGS

The teachings herein are described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 is a block diagram of an overall environment for performing lifecycle management of user-selected applications on wirelesscommunications devices.

FIG. 2 is a combined block and flow diagram of methods related toselling advertising space on the wireless communications devices.

FIG. 3 is a block diagram of a plurality of different profiles that maybe supported by the wireless communications devices.

FIG. 4 is a flow diagram of a process performed when the wirelesscommunications devices receive terminating or incoming communications.

FIG. 5 is a flow diagram of a process performed when the wirelesscommunications devices initiate outgoing communications.

FIG. 6 is a block diagram of illustrative components of a communicationsservice provider, suitable for supporting life cycle management ofuser-selected applications on wireless communications devices.

FIG. 7 is a block diagram of illustrative functions that may beperformed by an application life cycle maintenance management server, asshown in FIG. 6.

DETAILED DESCRIPTION

FIG. 1 illustrates an overall environment 100 for performing life cyclemanagement of user-selected applications on wireless communicationsdevices. A customer or user, illustrated in FIG. 1 as a “subscriber” 102may use a communication device, illustrated in FIG. 1 as a “subscriberdevice” 104, and may obtain services related thereto. It should beappreciated that the term “subscriber” includes not only a user with asubscription to a communication service for a communication device butalso an authorized user of the communication service for thecommunication device. Moreover, although one subscriber and onesubscriber device are shown in FIG. 1 for simplicity of illustration, itshould be appreciated that any number of subscribers and subscriberdevices may be used.

The device 104 may include one or more processors 106 that communicatewith one or more instances of machine-readable or computer-readablestorage media 108. The media 108 may store software that may be loadedinto the processor 106 and executed, thereby causing the device 104 toperform the various functions described herein. More specifically, themedia 108 may store one or more applications 110. FIG. 1 shows twoapplications 110A and 110N for convenience only, but the media 108 maycontain any number of applications.

The applications 110 may be characterized as core functions, representedgenerally at block 112, or as subscriber-selected functions, representedgenerally at block 114. Generally, the core functions 112 may beinstalled on the device 104 as a minimum configuration, and may includeapplications related to authenticating subscribers, registering thedevices on communications networks, handling over the devices from onecell or network to another, providing voice communications and voicemail services, or the like.

The subscriber-selected functions 114 may provide extra featuresadditional to the core functions 112. The subscriber 102 may select oneor more of these functions for installation on the device 104, either atthe time of purchasing the device 104 or some time afterwards. Examplesof the subscriber-selected functions 114 may include applicationsrelated to e-mailing, voice over IP (VoIP) functions, instant messaging(IMing), chat clients, location, video on demand, multi-player gaming orthe like.

The media 108 may include a menu presentation module 116 that assemblesa menu containing one or more available applications 118 for selectionand installation on the device 104. The menu presentation module 116 maypresent the menu to the subscriber using the device 104. The availableapplications 118 may correspond to the subscriber-selected functions114. By selecting one or more of the available applications presented onthe menu, the subscriber may configure the device 104 to perform any ofthe subscriber-selected functions 114, FIG. 1 shows two availableapplications 118A and 118N for convenience of illustration only, but theenvironment 100 may include any number of available applications.

One or more application providers 120 may provide the availableapplications 118 to a communications services provider 122. In thecourse of obtaining rights to use the device 104 and accessing servicesrelated thereto, the subscriber 102 may interact or contract with theservices provider. In turn, the services provider 122 may haverelationships with one or more of the application providers 120. Theapplication providers 120 may be related or unrelated to the servicesprovider 122. For example, one or more of the application providers 120may be third-party software vendors, relative to the services provider.

The device 104 may be responsive to subscriber input, selecting one ormore of the available applications, for installation. In this manner,the environment 100 enables the subscriber 102 to customize the devicewith applications 118 suited to his or her particular purposes.

The applications 118 may include standalone client applications thatreside and execute only on the device 104, or may include clientapplications that interact with one or more server applications on thecommunication services provider 122. Additionally, the clientapplications 118 may interact with one or more server applicationsprovided by third parties, with these server applications accessiblethrough a network associated with the communication services provider122.

Having described the environment 100 with FIG. 1, the discussion nowturns to a description of methods related to selling advertising spaceon the wireless communications devices, now presented with FIG. 2.

FIG. 2 illustrates components and flows related to methods for sellingadvertising space on the wireless communications devices. As describedabove in FIG. 1, the subscribers 102A and 102N may obtain correspondingdevices 104A and 104N from the services provider 122. The devices 104Aand 104N may include respective advertisement presentation modules 202Aand 202N (collectively, advertisement presentation modules 202). Theseadvertisement presentation modules may be similar to the menupresentation module 116 shown in FIG. 1. However, the advertisementpresentation module 202A may present one or more advertisements 204A and204N (collectively, advertisements 204) to the subscriber 102A via thedevice 104A, and the advertisement presentation module 202N may presentone or more advertisements 206A and 206N (collectively, advertisements206) to the subscriber 102N via the device 104N.

One or more advertisers 208 may provide the advertisements 204 and 206,through the services provider 122. FIG. 2 shows two advertisers 208A and208N for convenience only, but any number of advertisers could beincluded. In exchange for placing their advertisements before thesubscribers 102 via the devices 104, the advertisers 208 may providerespective payments 210A and 210N to the services provider.

In addition, the services provider 122 may intelligently selectadvertisements to be presented to the subscribers by querying a database212. For example, the database 212 may store information reflecting pasttransactions conducted between the services provider and the subscribers102. The database 212 may store demographic profiles of the subscribers.In other instances, the database 212 may store information pertaining torelationships with third parties. For example, the services provider andsuch third parties may enter into branding or marketing arrangements, sothat the customers of the third parties may subscribe to the servicesoffered by the services provider on some set of terms.

In any event, the services provider may query the database 212 with someidentifier associated with a given subscriber, denoted generally asquery 214. In response to the query, the database may return one or moreads that are selected specifically for the subscriber, based on, forexample, preferences or past history associated with the subscriber.These ads may be provisioned onto the device, so that when thesubscriber first powers-on the device, or at any time afterwards, theads are presented on the device.

Having described the components and data flows in FIG. 2, the discussionnow turns to a description a plurality of different profiles that may besupported by the subscriber devices 104, now presented with FIG. 3.

FIG. 3 illustrates a plurality of different profiles 302 that may besupported by the subscriber devices 104. For example only, but notlimitation, FIG. 3 shows an example subscriber device 104 associatedwith two profiles 302A and 302N, but single instances of the subscriberdevices could support any number of different profiles. For example, asubscriber could configure his or her device with a profile forwork-related use, and a profile for personal use. In other examples, thesubscriber may define profiles pertaining to volunteer work, charitableactivities, board-of-directors positions, or the like.

The various profiles 302 may be associated with one or more applications304 and 306 that are available under the different profiles 302. Forexample, a subscriber may use an enterprise e-mail application providedby his or her employer for work purposes, but may use a more basice-mail application for personal correspondence. In any event, FIG. 3shows the profile 302A as associated with any number of applications304A and 304N, and the profile 302N as associated with any number ofapplications 306A and 306N.

The applications 304 and 306 may be associated with respective addressbooks or other forms of contact lists, denoted generally at 308 and 310.More specifically, FIG. 3 shows the application 304A associated with anaddress book 308A, and the application 304N associated with an addressbook 308N. FIG. 3 also shows the application 306A associated with anaddress book 310A, and the application 306N associated with an addressbook 310N.

The various address books 308 and/or 310 may include various instancesof contact information 312 and/or 314. This contact information maygenerally take any form suitable for addressing voice or datacommunications to a person, or for receiving such communications from aperson. For example, the contact information may include phone numbers(e.g., 316A and 316N, collectively 316), addresses (e.g., 318A and 318N,collectively 318), or the like. The addresses 318 may take the form ofnetwork addresses, IP addresses, e-mail addresses, street address,Global Positioning Satellite coordinates or any other convenient form.

At any given time, the subscriber 102 may make one or more of theprofiles 302 active, as denoted by blocks 320. When different ones ofthe profiles are active, the applications and address bookscorresponding to the active profiles are available for execution. Forexample, if the subscriber 102 has defined a profile 302 forwork-related purposes, the subscriber may have that work-related profileactive whenever the subscriber is “on call” to respond to work-relatedmatters.

Having described the profiles in connection with FIG. 3, the discussionnow turns to a description of how these profiles may be used to handleincoming or outgoing communications, now presented with FIGS. 4 and 5.

FIG. 4 illustrates a process 400 that may be performed when thesubscriber devices (e.g., 104) receive terminating or incomingcommunications. While the process 400 is described in connection withcertain components illustrated herein, it is noted that some or all ofthe process 400 may be performed with other components without departingfrom the scope of the description herein.

Block 402 represents receiving the incoming communication at thesubscriber devices. These communications may take the form of incomingvoice calls arriving via one or more circuit-switched or packet-switchedcommunications network, or may be data communications (e.g., audio orvideo streams, e-mails, or the like).

Block 404 represents obtaining a telephone number, network address (asmight be used in VoIP communications), or other similar identifier,indicating where the incoming communication is directed. For example, ifan incoming voice call is directed to (555) 555-1212, then block 404 mayinclude obtaining this dialed number. Block 404 may thus include usingthe Dialed Number Information Service (DNIS), or other equivalents.

Block 406 represents searching one or more profiles associated with thedevice that receives the incoming communication. FIG. 3 shows examplesof the profiles at 302. More specifically, block 406 may includesearching contact information records (e.g., 312 and/or 314) for anycontact that matches the incoming identifier obtained in block 404.

Decision block 408 may include evaluating whether the incomingidentifier was located in any of the profiles. If not, the process 400takes No branch 410 to block 412. In block 412, the process 400 mayreport this condition to the subscriber, and prompt the subscriber forinstructions. In some instances, the process 400 may activate a defaultmode for the device, as represented generally in block 414. In block416, the process 400 may start an application associated with thisdefault mode. In these instances, the process 400 may omit thenotification shown in block 412, but may instead perform block 414and/or black 416 without providing the notification.

From block 408, if the incoming identifier was located in one of theprofiles, then the process 400 takes Yes branch 418 to block 420. Block420 represents placing the device into a mode corresponding to theprofile in which the incoming identifier was located. For example,referring briefly to FIG. 3, assume that the incoming identifier of thephone number (555) 555-1212 was located under the profile 302A. In thisscenario, block 420 may include placing the device into its business orprofessional mode.

Block 422 represents activating one or more applications in response tolocating the incoming identifier in blocks 406 and 408. For example,assume that the profile 302A is associated with a business orprofessional mode, and, as such, is associated with one or moreenterprise-type applications 304. Block 422 may include activating theseapplications so that the subscriber may readily use them to respond orprocess the incoming communication.

FIG. 5 illustrates a process 500 that may be performed when the wirelesscommunications devices initiate outgoing communications. While theprocess 500 is described in connection with certain componentsillustrated herein, it is noted that some or all of the process 500 maybe performed with other components without departing from the scope ofthe description herein.

Block 502 represents enabling the subscriber to configure the deviceinto one of a plurality of different operating modes (e.g., business,personal, or the like) and select an application with which to initiatethe outgoing communication, using a device such as the device 104. Block502 may include enabling the user to select a profile in which thedevice is to operate. Examples of profiles are shown in FIG. 3 at 320.

Block 504 represents loading any address books, contact lists, orsimilar structures for presentation to the subscriber. Block 504 mayinclude loading the entries in the address book into a menu structurefor review and selection by the subscriber.

Block 506 represents presenting the list of contacts to the subscriber.The contacts may be associated with one or more instances of contactinformation (e.g., telephone numbers, network or IP addresses, e-mailaddresses, chat or IM names, or the like). Block 506 may includepresenting these instances of contact information.

Block 508 represents receiving a selection of one of the contacts, as adestination or target of the outgoing communication. In instances wherea given contact is associated with more than one instance of contactinformation, block 508 may include enabling the subscriber to select thecontact information to use for the outgoing communication.

Finally, block 512 represents creating and sending a call detail recordrelating to the outgoing communication.

Having described the process flows with FIGS. 4 and 5, the discussionnow turns to a description of illustrative servers that may be includedin the communication services provider, now presented with FIG. 6.

FIG. 6 illustrates example components of the communications serviceprovider 122, suitable for supporting life cycle management ofuser-selected applications on wireless communications devices. Thedevice 104 may communicate with the provider 122 through a wirelessaccess point 602, which generally functions to provide a gateway into abroadband communications network. For example, the access point 602 maybe implemented as a wireless router that is compliant with WiFi (i.e.,IEEE 802.11) or WIMAX (i.e., IEEE 802.16) specifications to operatewithin unlicensed communication frequencies. Additionally, otherimplementations of the access point 602 may operate within licensedcommunication spectrum with a variety of broadband wireless IPprotocols: (e.g., WiMax, UMTS/HSDPA, CDMA EVDO, EDGE, and the like).

The communications service provider 122 may include one or moreapplication servers, as shown in FIG. 6. The configuration shown in FIG.6 is chosen for convenience only, but not to limit possibleimplementations of the communications service provider 122. Morespecifically, the various servers are shown only for ease of referencein describing different illustrative functions, and these functionscould be combined or redistributed among different servers withoutdeparting from the scope and spirit of the description herein.

Turning to the servers in more detail, some of the servers may berelated to core functions, such as those represented in FIG. 1 at block112. For example, a registration and authentication application server604 may handle core functions such as registering and authenticating thedevice 104 onto communication networks. A mobility management handoverapplication server 606 may administer the handing over of the devices104 from one cell to another as the devices move geographically. A VoIPapplication server 608 may store and distribute voice or data packetsrelated to ongoing conversations, in implementations using the Voice ofIP protocol. A menu application server 610 may control the display andchoices of applications that are available to the subscriber todownload. A billing application server 612 maintains billing and calldetail records relating to the various subscribers 102. As thesubscribers originate outgoing communications and/or receive in comingcommunications, the billing server 612 updates call detail recordsaccordingly.

An application life cycle maintenance management server 614 administerssubscriber-selected functions, such as those represented in FIG. 1 atblock 114. Generally, the management server 614 enables the subscribers102 to configure their devices 104 as most appropriate for theirintended uses, enabling the subscribers to download and installparticular applications. Further details relating to functions performedby the management server 614 are now provided with FIG. 7.

An advertising application server 616 may store the advertisements thatare presented to the subscribers 102 via the devices 104. Examples ofadvertisements are shown in FIG. 2 at 204 and 206. FIG. 2 also showsexample advertisement presentation modules at 202. The advertisingapplication server 616 may, for example, push advertising content to theadvertisement presentation modules on the devices 104.

A location application server 618 may store and track the locations ofvarious subscriber devices 104. In this manner, the location applicationserver may enable the communication services provider to monitor thelocations of the devices 104 at any particular time.

A video on demand application server 620 may store video content thatmay be streamed on demand to the subscriber device 104. Thus, the videoon demand application server may enable subscribers to access videocontent via the device 104.

A multiplayer gaming application 622 may store gaming content, andenable subscribers to access the gaming content via the devices 104. Insome instances, the multiplayer gaming application may enable two ormore of the subscribers to play games with one another, whether inadversarial or collaborative roles. In other instances, the multiplayergaming application may enable single subscribers to access the gamingcontent on a more solitary basis.

FIG. 7 illustrates several examples of functions that may be performedby the application life cycle maintenance management server 614, asshown in FIG. 6. As represented generally in block 702, the managementserver 614 may manage how the devices 104 are configured, for example,when the subscribers first obtain the devices 104 or at any timeafterwards. More specifically, the configuration management block 702may receive data representing a selection 704 made by a subscriber(e.g., the subscriber 102) of one or more applications (e.g., theapplications 110A and 110N) for installation on the device 104.

The configuration management block 702 may pass the selection 704through to a matching engine 706, which determines whether the selectedapplication may be installed on the device. The matching engine mayreceive data representing minimum configuration parameters 708 fordifferent respective applications 110. The matching engine may alsoreceive data representing capabilities 710 of particular devices, suchas the amount of available storage. It is assumed that the device 104 asshown in FIG. 7 is associated with the subscriber 102, such that thesubscriber has requested to install an application onto the device.

The matching engine 706 may compare the configuration parameters 708 fora given application to the capabilities 710 of a given device, todetermine whether the application may be installed on the device.Examples of these device capabilities may include memory capacity,processor speed, display capabilities, and the like. If the capabilities710 of the given device match or exceed the configuration parameters 708for the given application, then the application may be installed on thedevice. A match signal 712 may indicate whether the application may beinstalled on the device, and may pass from the matching engine to theconfiguration management block 702.

If the match signal 712 indicates that the application may be installedon the device, the configuration management block 702 may so install theapplication, as represented at 714. However, if the match signal 712indicates that the application is not a match for the device ascurrently configured, the configuration block 702 may recommend that thesubscriber delete one or more applications currently installed on thedevice, as represented at 716. Additionally, the configuration block 702may recommend that the subscriber upgrade to, a different device, asrepresented at 718. In this latter scenario, the configuration block 702may provision the upgraded device with the applications 110 previouslyselected by the subscriber.

Once the device is installed and configured with the selectedapplications, the management server 614 may administer any licensingissues related to these applications on an ongoing basis. Block 720represents this license administration function. Typically, thesubscriber, when installing applications onto the device, does notobtain ownership rights in the applications, but instead obtains alicense to use the application. These license rights may be subject tothe subscriber paying license fees and/or performing other obligations.These payments and other obligations may be tracked by the billingserver 612, shown in FIG. 6 and carried forward to FIG. 7 forconvenience.

If the subscriber remains current on any license payments related to agiven application, and performs any other obligations, then the licenseadministration block 720 grants the subscriber continued access to thegiven application, as represented at 722. However, if the subscriber isnot current on the license payments related to a given application, orfails to perform any other obligations, then the license administrationblock 720 may send a notification to the subscriber, detailing what thesubscriber may do to become current and maintain access to theapplications. If the subscriber does not become current, the licenseadministration block 720 may remove or disable the given application onthe subscriber's device, as represented at 724.

The management server 614 may also manage the client applicationsinstalled on the devices, as subsequent versions of those applicationsbecome available. For example, vendors providing those applications(e.g., the application providers 120 in FIG. 1) may introduce newfeatures, fix bugs present in earlier versions, or the like. In anyevent, an application version management block 726 may receive data 728representing versions of one or more applications currently installed onthe device. The version management block 726 may also receive data 730representing the newest versions of those applications. If the newestversions of the applications are not installed on the device, then theversion management block 726 may push updated versions of theapplications to the device. These updated versions are represented inFIG. 7 at 732. The updated versions 732 may be pushed to the devices 104when the devices 104 are in communication with the services provider 122and the management server 614.

Having provided the above description, several observations are nownoted. The tools and techniques described above for performing lifecycle management of user-selected applications on wirelesscommunications devices enable use of a client-services model formaintaining the applications on the devices, with the services provider122 (and related components) assuming a server role, and the variousdevices 104 assuming a client role. Additionally, the services provider122 and the management server 614 may provide a network-based, automatedplatform for configuring and managing application installed on a varietyof subscriber devices, thereby relieving the subscribers from thesetasks.

It is noted that the various modules and servers shown in the Figuresherein may be implemented in hardware, software, or any combinationthereof. Additionally, these modules and servers are shown as separateitems only for convenience of reference and description, and theserepresentations do not limit possible implementations of the teachingsherein. Instead, various functions described with these modules andservers could be combined or separated as appropriate in a givenimplementation, without departing from the scope and spirit of thedescription herein.

CONCLUSION

Although tools and techniques for performing life cycle management ofuser-selected applications on wireless communications devices have beendescribed in language specific to certain features and methods, it is tobe understood that the features defined in the appended claims are notnecessarily limited to the specific features and methods described.Rather, the specific features and methods are disclosed as illustrativeforms of implementing the claimed subject matter.

What is claimed is:
 1. A method, comprising: receiving, by a systemcomprising a processor, from a user interface of a mobile communicationsdevice, a first user input for configuring a first user profile to bemaintained at the mobile communications device; receiving, by thesystem, from the user interface of the mobile communications device, asecond user input for configuring a second user profile, distinct fromthe first profile, to be maintained at the mobile communications device;receiving, by the system, from the user interface of the mobilecommunications device, a third user input indicating the first userprofile and a first executable application to initiate an installationof the first executable application in association with the first userprofile at the mobile communications device; receiving, by the system,from the user interface of the mobile communications device, a fourthuser input indicating the second user profile and a second executableapplication to initiate an installation of the second executableapplication in association with the first user profile at the mobilecommunications device; initiating, by the system, in response to thethird user input, a storage of the first executable application at amemory of the mobile communications device such that the firstexecutable application is associated in the memory with the first userprofile maintained at the mobile communications device; and initiating,by the system, in response to the fourth user input, a storage of thesecond executable application at the memory of the mobile communicationsdevice such that the second executable application is associated in thememory with the second user profile maintained at the mobilecommunications device.
 2. The method of claim 1, further comprising:receiving a communication; and determining that the communication is notassociated with any pre-set user profile, including the first userprofile and the second user profile, at the mobile communicationsdevice.
 3. The method of claim 2, wherein: the first user profile isassociated with a first mode of operation for the mobile communicationsdevice; the second user profile is associated with a second mode ofoperation for the mobile communications device; and the method furthercomprises initiating a switching of the mobile communications device toa default mode, for processing the communication, in response todetermining that the communication is not associated with any pre-setuser profile at the mobile communications device, wherein the defaultmode differs from the first mode associated with the first user profileand the second mode associated with the second user profile.
 4. Themethod of claim 2, further comprising initiating a presentation, by themobile communications device, of a user notification in response todetermining that the communication is not associated with any pre-setuser profile, wherein the user notification indicates that the receivedcommunication is not associated with any pre-set user profile at themobile communications device.
 5. The method of claim 4, wherein thenotification includes a prompt requesting user instructions.
 6. Themethod of claim 1, further comprising initiating at least onepresentation, by the mobile communications device, of a plurality ofexecutable applications as options for installation at the mobilecommunications device, wherein: the first user input is received inresponse to the presentation of the plurality of executableapplications; and the second user input is received in response to thepresentation of the plurality of executable applications.
 7. The methodof claim 1, further comprising: receiving a communication; anddetermining that the communication is associated with the first userprofile at the mobile communications device.
 8. The method of claim 7,further comprising initiating, in response to determining that thecommunication is associated with the first user profile, a switching ofthe mobile communications device to a first mode associated with thefirst user profile at the mobile communications device.
 9. The method ofclaim 7, further comprising activating, in response to determining thatthe communication is associated with the first user profile, the firstexecutable application, associated with the first user profile at themobile communications device, for processing the communication received.10. The method of claim 7, wherein: the communication is a firstcommunication; and the method further comprises: receiving a secondcommunication; and determining that the second communication isassociated with the second user profile at the mobile communicationsdevice.
 11. The method of claim 10, further comprising initiating, inresponse to determining that the second communication is associated withthe second user profile, a switching of the mobile communications deviceto a second mode associated with the second user profile at the mobilecommunications device.
 12. The method of claim 10, further comprisingactivating, in response to determining that the second communication isassociated with the second user profile, the second executableapplication, associated with the second user profile at the mobilecommunications device, for processing the second communication received.13. The method of claim 1, wherein: the first user profile is associatedwith business use of the mobile communications device; and the seconduser profile is associated with personal use of the mobilecommunications device.
 14. The method of claim 1, wherein: the firstuser profile is associated with a first identifier and a first mode forthe mobile communications device; the second user profile is associatedwith a second identifier, being distinct from the first identifier, anda second mode for the mobile communications device; and the methodfurther comprises: obtaining a communication identifier from thecommunication; determining whether the communication identifier matchesan identifier of the first user profile and the second user profile; andplacing the device in the first mode in response to determining thecommunication identifier matches the first identifier.
 15. The method ofclaim 14, further comprising activating, in response to placing thedevice in the first mode, the first executable application, forprocessing the communication received.
 16. A system, comprising: aprocessor; and a computer-readable storage device comprising anon-transitory computer-executable instructions that, when executed bythe processor, cause the processor to perform operations comprising:receiving, from a user interface of a mobile communications device, afirst user input for configuring a first user profile to be maintainedat the mobile communications device; receiving, from the user interfaceof the mobile communications device, a second user input for configuringa second user profile, distinct from the first profile, to be maintainedat the mobile communications device; receiving, from the user interfaceof the mobile communications device, a third user input indicating thefirst user profile and a first executable application to initiate aninstallation of the first executable application in association with thefirst user profile at the mobile communications device; receiving, fromthe user interface of the mobile communications device, a fourth userinput indicating the second user profile and a second executableapplication to initiate an installation of the second executableapplication in association with the first user profile at the mobilecommunications device; initiating, in response to the third user input,a storage of the first executable application at a memory of the mobilecommunications device such that the first executable application isassociated in the memory with the first user profile maintained at themobile communications device; and initiating, in response to the fourthuser input, a storage of the second executable application at the memoryof the mobile communications device such that the second executableapplication is associated in the memory with the second user profilemaintained at the mobile communications device.
 17. The system of claim16, wherein: the first user profile is associated with a firstidentifier and a first mode for the mobile communications device; thesecond user profile is associated with a second identifier, beingdistinct from the first identifier, and a second mode for the mobilecommunications device; and the operations further comprise: obtaining acommunication identifier from the communication; determining whether thecommunication identifier matches an identifier of the first user profileand the second user profile; and placing the device in the first mode inresponse to determining the communication identifier matches the firstidentifier.
 18. The system of claim 17, wherein the operations furthercomprise activating, in response to placing the device in the firstmode, the first executable application, for processing the communicationreceived.
 19. The system of claim 16, wherein: the first user profile isassociated with business use of the mobile communications device; andthe second user profile is associated with personal use of the mobilecommunications device.
 20. A computer-readable storage device comprisinga non-transitory computer-executable instructions that, when executed bya processor, cause the processor to perform operations comprising:receiving, from a user interface of a mobile communications device, afirst user input for configuring a first user profile to be maintainedat the mobile communications device; receiving, from the user interfaceof the mobile communications device, a second user input for configuringa second user profile, distinct from the first profile, to be maintainedat the mobile communications device; receiving, from the user interfaceof the mobile communications device, a third user input indicating thefirst user profile and a first executable application to initiate aninstallation of the first executable application in association with thefirst user profile at the mobile communications device; receiving, fromthe user interface of the mobile communications device, a fourth userinput indicating the second user profile and a second executableapplication to initiate an installation of the second executableapplication in association with the first user profile at the mobilecommunications device; initiating, in response to the third user input,a storage of the first executable application at a memory of the mobilecommunications device such that the first executable application isassociated in the memory with the first user profile maintained at themobile communications device; and initiating, in response to the fourthuser input, a storage of the second executable application at the memoryof the mobile communications device such that the second executableapplication is associated in the memory with the second user profilemaintained at the mobile communications device.